Providing services for logical networks

ABSTRACT

Some embodiments provide a method for a network controller that manages several logical networks. The method receives a specification of a logical network that includes at least one logical forwarding element attached to a logical service (e.g., DHCP). The method selects at least one host machine to host the specified logical service from several host machines designated for hosting logical services. The method generates logical service configuration information for distribution to the selected host machine. In some embodiments, the method selects a master host machine and a backup host machine for hosting logical service. In some embodiments, a particular one of the designated host machines hosts at least two DHCP services for two different logical networks as separate processes operating on the particular host machine.

CLAIM OF BENEFIT TO PRIOR APPLICATION

This application claims the benefit of U.S. Provisional Application61/866,022, filed Aug. 14, 2013. U.S. Application 61/866,022 isincorporated herein by reference.

BACKGROUND

Typical physical networks often use Dynamic Host Configuration Protocol(DHCP) to assign IP addresses to physical machines. When a computerboots up, one of the processes that computer performs is to communicatewith one or more DHCP servers to request and receive an IP address. Thisassignment may be static (a given computer always receives the same IPaddress based on its MAC address) or dynamic (the DHCP server assigns anIP address from a range of addresses, and a given computer may receivedifferent IP addresses at different times).

In virtualized networks, virtual machines also require IP addresses.With the number of virtual machines that may operate in a multi-tenantdata center, having a single DHCP server or even several DHCP serversoperating to serve all of the virtualized networks in a data center maynot be feasible, especially in the bootstorm case (when numerous VMs arestarted up at the same time). Thus, methods for providing DHCP serviceto such virtualized networks are needed.

BRIEF SUMMARY

Some embodiments provide a network control system that enables DynamicHost Configuration Protocol (DHCP) services for logical networks.Specifically, the network control system of some embodiments enables theprovisioning of DHCP services in a centralized manner accessible by allof the machines connected to a logical network. In some embodiments, thenetwork control system provides DHCP services within a service node thatis part of the logical network, and which may additionally provide otherservices (e.g., metadata proxy, DNS, etc.).

In some embodiments, a user (e.g., an administrator) may configure alogical network (e.g., a collection of logical switches, routers,middleboxes, services, etc.) for implementation across a physicalnetwork (e.g., numerous host machines in a multi-tenant data center). Insome embodiments, the logical network may include logical service nodes,which provide the DHCP services in addition to other services, asmentioned above. The user may configure the logical service nodes toattach to one or more logical switches in the logical network in someembodiments.

The network control system comprises a controller cluster (one or morenetwork controllers, which are hierarchically arranged in someembodiments), which selects one or more host machines on which toimplement the logical service node. In some embodiments, the physicalnetwork on which the logical networks are implemented includes a set ofhost machines specifically for hosting the logical service nodes. Insome embodiments, each of these host machines may host several logicalservice nodes, and the controller cluster is responsible for balancingthe logical service nodes of various logical networks (e.g., fordifferent tenants) across this set of host machines.

In some embodiments, the network controller cluster selects two hostmachines from the set to implement each logical service node, with afirst host machine acting as a master (or active) implementation and asecond host machine acting as a backup (or standby) implementation.Thus, a particular one of the host machines may have the masterimplementations of several different logical service nodes, the backupimplementations of several different logical service nodes, or acombination thereof.

On the host machines, some embodiments implement the logical servicenodes in a container that runs on the machine, such as a virtual machineor a namespace. A namespace, in some embodiments, is a lightweightcontainer (less computationally intensive than a virtual machine) thatcan operate on a host machine. Various processes can run in a namespace.Thus, with each logical service node implemented by a namespace runningon a host machine, each of the services provided by that node may run asprocesses in the namespace. For DHCP service, a DHCP module (e.g., anopen source dhcp daemon) runs in the namespace. Each of the namespacesoperating on a particular host may have a different instance of the DHCPmodule operating a DHCP service for a different logical network. Asmentioned above, in some embodiments logical switches (logicalconstructs for performing L2 forwarding based on, e.g., MAC addresses)connect to the logical services node that contains the DHCP service. Insome embodiments, multiple logical switches on a network may connect tothe same logical services node.

When a user configures a DHCP service for a logical network, thecontroller cluster of some embodiments generates data tuples thatrepresent the DHCP configuration. In order to specify the DHCPconfiguration, in some embodiments the user specifies a logical servicesnode, attaches one or more logical switches to the node, providesMAC-to-IP bindings (i.e., for static DHCP) and DHCP options for themachines connected to the logical switch, among other actions. Thecontroller cluster, in addition to specifying one or more host machineson which to implement the service, then transforms this configurationinto a set of data tuples that define a namespace, defines a DHCPprocess for the namespace, defines the logical switch, and defines theDHCP configuration (including the address bindings and options). Someembodiments provide static DHCP, in which the address bindings map eachMAC address of the machines connected to the logical switch to aspecific IP address. The DHCP options may be global (i.e., for all hostson all logical switches that use the particular DHCP service), appliedto a particular logical switch (i.e., for all hosts on the logicalswitch), or applied to a specific host.

The controller cluster is responsible for distributing these data tuplesto the appropriate host machines (e.g., the master and backup hosts fora particular logical service node). These host machines receive the datatuples and store the tuples as database tables having a particularformat. In some embodiments, the data tuples are received in a similarformat to data tuples relating to virtual switch configuration on thehost machine, and are stored in the same database.

In some embodiments, a module (e.g., a namespace daemon) that operateson the host machine monitors the database for changes relating tological services nodes, and is responsible for starting up the DHCPservice based on the database table entries. This namespace daemoncreates the namespace on the host machine, and starts the DHCP moduleoperating in the namespace. In addition, the namespace daemon generatesa configuration file for the DHCP module that defines the DHCPconfiguration from the user in language readable by the DHCP module.

This configuration file is a text file in some embodiments with datawritten in a meta-language of the DHCP module. To generate theconfiguration file, the namespace daemon of some embodiments defines thelogical switch as a subnet, and defines the MAC-to-IP bindings for thesubnet in the configuration file. In addition, the namespace daemondefines the options in the configuration file. However, some options maybe available for the logical DHCP service, but not supported by the DHCPmodule implementing that DHCP service. For these options, the namespacedaemon determines a way to implement the specified option in theconfiguration file with features that are supported by the DHCP module(e.g., by using a combination of supported options, definitions, etc.).

When modifying the DHCP configuration for a particular service, in someembodiments the namespace daemon can either modify the configurationfile and then restart the DHCP module, or perform the modificationswhile the DHCP module is running (without a restart). Some embodimentsonly perform certain smaller, more common modifications (e.g., changesto host-specific options, modifications to single host MAC:IP bindings,etc.) during runtime. Other, larger modifications (e.g., per logicalswitch or global options, addition or removal of a logical switch, etc.)require a restart.

Once the DHCP module is operational, machines on a logical switchconnected to the logical service node can use the DHCP service. BecauseDHCP packets are broadcast, when a machine (e.g., a virtual machine)sends out a DHCP discovery packet, the forwarding element located on thehost machine with the VM sends the packet to all destinations on thelogical switch in some embodiments. This includes the logical servicenode, as well as all other VMs (which ignore the packet). When thelogical service node is implemented on two host machines, with an activeand a standby implementation, the forwarding element at the VM's hostmachine sends the DHCP discovery packet to only the activeimplementation (e.g., via a tunnel between the hosts). The DHCP modulereceives the packet, and the DHCP process proceeds according to protocolin some embodiments.

The preceding Summary is intended to serve as a brief introduction tosome embodiments of the invention. It is not meant to be an introductionor overview of all inventive subject matter disclosed in this document.The Detailed Description that follows and the Drawings that are referredto in the Detailed Description will further describe the embodimentsdescribed in the Summary as well as other embodiments. Accordingly, tounderstand all the embodiments described by this document, a full reviewof the Summary, Detailed Description and the Drawings is needed.Moreover, the claimed subject matters are not to be limited by theillustrative details in the Summary, Detailed Description and theDrawing, but rather are to be defined by the appended claims, becausethe claimed subject matters can be embodied in other specific formswithout departing from the spirit of the subject matters.

BRIEF DESCRIPTION OF THE DRAWINGS

The novel features of the invention are set forth in the appendedclaims. However, for purpose of explanation, several embodiments of theinvention are set forth in the following figures.

FIG. 1 conceptually illustrates a logical network architecture of someembodiments that includes a logical service node.

FIG. 2 conceptually illustrates a physical implementation of the logicalnetwork architecture of FIG. 1 according to some embodiments.

FIG. 3 conceptually illustrates a network control system of someembodiments for configuring managed forwarding elements and logicalservice nodes in order to implement logical networks.

FIG. 4 conceptually illustrates the propagation of data through thehierarchical network control system of some embodiments.

FIG. 5 conceptually illustrates a process performed by the logicalcontroller in some embodiments to assign a newly created DHCP serviceand its corresponding logical service node to a set of host machines.

FIG. 6 conceptually illustrates a service host cluster that includesfour host machines.

FIG. 7 conceptually illustrates a process performed by the logicalcontroller in some embodiments to configure a DHCP service for a logicalservice node.

FIG. 8 conceptually illustrates a software architecture of someembodiments for a host.

FIG. 9 conceptually illustrates a process of some embodiments forstarting up a new DHCP service on a logical service node host.

FIG. 10 conceptually illustrates a process of some embodiments formodifying an existing DHCP configuration of an operating DHCP module.

FIG. 11 conceptually illustrates a namespace daemon of some embodiments.

FIG. 12 conceptually illustrates a process of some embodiments forgenerating a configuration file for a DHCP module based on a set ofdatabase table entries defining a DHCP configuration.

FIG. 13 conceptually illustrates a process of some embodiments performedby a DHCP service in a logical network.

FIG. 14 illustrates a logical network, its implementation in a physicalnetwork, and a DHCP discovery packet sent by one of the VMs of thelogical network.

FIG. 15 conceptually illustrates an electronic system with which someembodiments of the invention are implemented.

DETAILED DESCRIPTION

In the following detailed description of the invention, numerousdetails, examples, and embodiments of the invention are set forth anddescribed. However, it will be clear and apparent to one skilled in theart that the invention is not limited to the embodiments set forth andthat the invention may be practiced without some of the specific detailsand examples discussed.

Some embodiments provide a network control system that enables DynamicHost Configuration Protocol (DHCP) services for logical networks.Specifically, the network control system of some embodiments enables theprovisioning of DHCP services in a centralized manner accessible by allof the machines connected to a logical network. In some embodiments, thenetwork control system provides DHCP services within a service node thatis part of the logical network, and which may additionally provide otherservices (e.g., metadata proxy, DNS, etc.).

In some embodiments, a user (e.g., an administrator) may configure alogical network (e.g., a collection of logical switches, routers,middleboxes, services, etc.) for implementation across a physicalnetwork (e.g., numerous host machines in a multi-tenant data center). Insome embodiments, the logical network may include logical service nodes,which provide the DHCP services in addition to other services, asmentioned above. The user may configure the logical service nodes toattach to one or more logical switches in the logical network in someembodiments.

FIG. 1 conceptually illustrates such a logical network architecture 100of some embodiments. As shown, the logical network 100 includes twological switches 105 and 110, a logical router 115, and a logicalservice node 120. Each of the logical switches 105 and 110 connectsseveral virtual machines (in this case, two virtual machines (VMs) areconnected by each logical switch), and the logical router 115 connectsthe two logical switches (i.e., logical L2 domains) together.

In addition, the logical service node 120 connects to the logicalswitches 105 and 110 in order to provide various network services to thelogical switches (i.e., to entities connected to logical switches, suchas VMs, physical servers connected through top of rack switches, L2segments, etc.). In some embodiments, these network services includeDHCP, metadata proxy, DNS, DHCP relay, and other services. Metadataproxy, in some embodiments, is a service accessed by virtual machines ina datacenter that provides various information to the virtual machines.When VMs start up, a program on the VM sends a request to a static IPaddress to request information about itself, such as what type of VM itis, the time zone in which it is located, what type of networkingresources are available, etc. The metadata proxy service at this staticIP address provides this information to the VM. In some embodiments,this service is implemented within a logical service node.

In some embodiments, the logical network architecture is restricted suchthat only logical switches can connect to logical service nodes thatprovide these network services. However, as shown in this example,multiple logical switches may connect to the logical service nodes insome embodiments. Even with such restrictions, one of ordinary skill inthe art will recognize that multiple different logical networkarchitectures may be created. For example, the logical router might havea connection to external networks, additional logical switches may beconnected to the logical router, etc.

FIG. 2 conceptually illustrates a physical implementation 200 of thelogical network architecture 100 according to some embodiments. Asshown, some embodiments implement the logical switching and routingelements (collectively referred to as logical forwarding elements) in adistributed, virtualized fashion. That is, rather than using physicalswitches and routers to implement the logical forwarding elements, theforwarding responsibilities are spread across managed forwardingelements (MFEs) distributed throughout the network. For instance, someembodiments include packet processing (i.e., switching and routing)software within the physical host machines that host the VMs (e.g.,running on top of or within virtualization software on the host). Thispacket processing software (e.g., open virtual switch (“OVS”))implements the logical forwarding elements of one or more logicalnetworks in some embodiments.

In this case, the logical forwarding elements 105-115 of the network 100are distributed across three host machines 205-215 that host the virtualmachines connected through the logical network 100. In some embodiments,as shown, the MFE on each of these hosts implements all of the logicalforwarding elements of the network. The first host 205 hosts VM1, whichconnects to logical switch 105. However, the MFE 220 on this hostimplements the logical switch 110 and the logical router 115 in additionto the logical switch 105. In some embodiments, all or most of thelogical processing on a packet is performed at the first MFE thatreceives the packet. For traffic originating at a VM, this first hop isthe MFE at the host on which the VM operates. As such, if the VM sendspackets to a VM on a different logical switch (e.g., VM1 sending apacket to VM3), the MFE at that host needs to be able to process thepacket through its logical switch as well as the connecting logicalrouter and the destination logical switch.

Unlike the logical forwarding elements, the DHCP and other servicesprovided by the logical service node are not distributed in someembodiments. The physical implementation 200 of the logical networkincludes two logical service node hosts 225 and 230. Each of the hostmachines 205-215 that implements the logical network 100 connects toboth of these service node host machines 225 and 230.

As indicated in the figure, while the logical service node 120 isimplemented on two service node hosts 225 and 230, one of these is anactive (or master) implementation 235 (on host 225) and the other is astandby (or backup) implementation 240 (on host 230). In someembodiments, the physical network in which the logical networks areimplemented includes a set of host machines specifically for hosting thelogical service nodes, and each of these host machines may host severallogical service nodes. In other embodiments, the cluster of hostmachines for hosting logical service nodes may also host (i) centralizedlogical routers for logical networks and/or (ii) L3 gateways forprocessing L3 traffic in and out of the managed network. Although theexample logical network in FIG. 2 shows the logical router 115implemented in a distributed fashion in the MFEs residing on hosts205-215, in some embodiments all L3 traffic is sent to a separatecentralized host machine for routing. Furthermore, if the logical router115 included a port that connected to an external unmanaged network,some embodiments use a L3 gateway for processing traffic in and out ofthat port.

In some embodiments, the physical infrastructure that implements thelogical networks is managed by a network control system, including acontroller cluster (one or more network controllers, which arehierarchically arranged in some embodiments). The controller cluster, inaddition to managing the MFEs at the host machines, is responsible forbalancing the logical service nodes of various logical networks (e.g.,for different tenants) across the aforementioned set of host machinesfor the logical service nodes.

In some embodiments, the network controller cluster selects two hostmachines from the set to implement each logical service node, with afirst host machine operating the active implementation and a second hostmachine operating the standby implementation. Thus, a particular one ofthe host machines may have the master implementations of severaldifferent logical service nodes, the backup implementations of severaldifferent logical service nodes, or a combination thereof. For instance,the logical service node host 225 that has the active logical servicenode implementation might also host the standby logical service node fora different logical network.

While the examples described herein use one active and one standbyimplementation for each logical service nodes, different embodiments mayimplement logical service nodes in different configurations. Forexample, some embodiments select two or more host machines to implementeach logical service node, with each of these implementations active(rather than having a backup). When a VM or other host sends a requestto the logical service node, the MFE to which that VM/host connectsselects one of the several active logical service node implementationsas a destination for the packet. For multi-stage DHCP (e.g., thestandard discovery/offer/request/acknowledgement operation of theprotocol), the MFE ensures that all packets from a given source are sentto the same logical service node host. In the case of static DHCP, nocommunication is required between the active logical service nodeimplementations. For dynamic DHCP, on the other hand, the various activeimplementations share state so as to keep up to date on which IPaddresses have been assigned.

The logical service nodes 235 and 240 are implemented in containers thatrun on the host machines 225 and 230 in some embodiments, such asvirtual machines or namespaces. A namespace, in some embodiments, is alightweight container (less computationally intensive than a virtualmachine) that can operate on a host machine. Various processes can runin a namespace. Thus, with each logical service node implemented by anamespace running on a host machine, each of the services provided bythat node may run as processes in the namespace. For DHCP service, aDHCP module (e.g., an open source dhcp daemon) runs in the namespace.Each of the namespaces operating on a particular host may have adifferent instance of the DHCP module operating a DHCP service for adifferent logical network.

When a user configures a DHCP service for a logical network, thecontroller cluster of some embodiments generates data tuples thatrepresent the DHCP configuration. In order to specify the DHCPconfiguration, in some embodiments the user specifies a logical servicesnode, attaches one or more logical switches to the node, providesMAC-to-IP bindings (i.e., for static DHCP) and DHCP options for themachines connected to the logical switch, among other actions. Thecontroller cluster, in addition to specifying one or more host machineson which to implement the service, then transforms this configurationinto a set of data tuples that define a namespace, defines a DHCPprocess for the namespace, defines the logical switch, and defines theDHCP configuration (including the address bindings and options). Someembodiments provide static DHCP, in which the address bindings map eachMAC address of the machines connected to the logical switch to aspecific IP address. The DHCP options may be global (i.e., for all hostson all logical switches that use the particular DHCP service), appliedto a particular logical switch (i.e., for all hosts on the logicalswitch), or applied to a specific host.

The controller cluster is responsible for distributing these data tuplesto the appropriate host machines (e.g., the master and backup hosts fora particular logical service node). These host machines receive the datatuples and store the tuples as database tables having a particularformat (e.g., OVSdb). In some embodiments, the data tuples are receivedin a similar format to data tuples relating to virtual switchconfiguration on the host machine, and are stored in the same database.

In some embodiments, a module (e.g., a daemon) that operates on the hostmachine monitors the database for changes relating to logical servicesnodes, and is responsible for starting up the DHCP service based on thedatabase table entries. This namespace daemon creates the namespace onthe host machine, and starts the DHCP module operating in the namespace.In addition, the namespace daemon generates a configuration file for theDHCP module that defines the DHCP configuration from the user inlanguage readable by the DHCP module.

This configuration file is a text file in some embodiments with datawritten in a particular language readable by the DHCP module. Togenerate the configuration file, the namespace daemon of someembodiments defines the logical switch as a subnet, and defines theMAC-to-IP bindings for the subnet. In addition, the namespace daemondefines the options in the configuration file. However, some options maybe available for the logical DHCP service, but not supported by the DHCPmodule implementing that DHCP service. For these options, the namespacedaemon determines a way to implement the specified option in theconfiguration file with features that are supported by the DHCP module(e.g., by using a combination of supported options, definitions, etc.).

When modifying the DHCP configuration for a particular service, in someembodiments the namespace daemon can either modify the configurationfile and then restart the DHCP module, or perform the modificationswhile the DHCP module is running (without a restart). Some embodimentsonly perform certain smaller modifications (e.g., changes tohost-specific options, modifications to single host MAC:IP bindings,etc.) during runtime. Other, larger modifications (e.g., per logicalswitch or global options, addition or removal of a logical switch, etc.)require a restart.

Once the DHCP module is operational, machines on a logical switchconnected to the logical service node can use the DHCP service. BecauseDHCP packets are broadcast, when a machine (e.g., a virtual machine)sends out a DHCP discovery packet, the forwarding element located on thehost machine with the VM sends the packet to all destinations on thelogical switch in some embodiments. This includes the logical servicenode, as well as all other VMs (which ignore the packet). When thelogical service node is implemented on two host machines, with an activeand a standby implementation, the forwarding element at the VM's hostmachine sends the DHCP discovery packet to only the activeimplementation (e.g., via a tunnel between the hosts). The DHCP modulereceives the packet, and the DHCP process proceeds according to protocolin some embodiments.

The term “packet” is used here as well as throughout this application torefer to a collection of bits in a particular format sent across anetwork. One of ordinary skill in the art will recognize that the termpacket may be used herein to refer to various formatted collections ofbits that may be sent across a network, such as Ethernet frames, TCPsegments, UDP datagrams, IP packets, etc.

The above description introduces the provision of services, specificallyDHCP, for logical networks of some embodiments. Several more detailedembodiments are described below. First, Section I describes theprovisioning of logical service nodes and DHCP by the network controlsystem of some embodiments. Section II then describes the generation ofa DHCP configuration on the host based on the information received fromnetwork controllers in some embodiments. Next, Section III describesruntime DHCP processing of some embodiments once a logical service nodeis configured. Finally, Section IV describes an electronic system withwhich some embodiments of the invention are implemented.

I. DHCP Configuration by Network Controllers

As mentioned, in some embodiments a network control system sets up andconfigures the DHCP service for a logical network. One or more networkcontrollers in the network control system receive the DHCP configurationinput by an administrator and convert this information into data tuplesthat can be read by the host machine(s) which implement the DHCPservice, in addition to selecting the one or more host machines to usefor the service. The network control system also distributes the datatuples to these host machines.

FIG. 3 conceptually illustrates such a network control system of someembodiments for configuring managed forwarding elements and logicalservice nodes in order to implement logical networks. As shown, thenetwork control system 300 includes an input translation controller 305,a logical controller 310, physical controllers 315 and 320, hosts325-340, and two logical service node hosts 345 and 350. As shown, thehosts 325-340 (as well as the logical service node hosts 345 and 350)include managed forwarding elements, which may be implemented as shownabove in FIG. 2. One of ordinary skill in the art will recognize thatmany other different combinations of the various controllers and hostsare possible for the network control system 300.

In some embodiments, each of the controllers in a network control systemhas the capability to function as an input translation controller,logical controller, and/or physical controller. Alternatively, in someembodiments a given controller may only have the functionality tooperate as a particular one of the types of controller (e.g., as aphysical controller). In addition, different combinations of controllersmay run in the same physical machine. For instance, the inputtranslation controller 305 and the logical controller 310 may run in thesame computing device, with which a data center management applicationinteracts (or with which an administrator interacts directly).

The input translation controller 305 of some embodiments includes aninput translation application that translates network configurationinformation received from a user. While shown as receiving theinformation directly from a user, in some embodiments a user interactswith a data center management application, which in turn passes thenetwork configuration information to the input translation controller.

For example, a user may specify a network topology such as that shown inFIG. 1. For each of the logical switches, the user specifies themachines that connect to the logical switch (i.e., to which logicalports are assigned for the logical switch). The user may also specifywhich logical switches attach to any created logical service nodes,which logical services should be offered by each logical services node,and the configurations for those logical services. The input translationcontroller 305 translates the entered network topology into logicalcontrol plane data that describes the network topology. For example, anentry might state that a particular MAC address A is located at a firstlogical port X of a particular logical switch, or that a logical servicenode Q is located at a second logical port Y of the particular logicalswitch.

In some embodiments, each logical network is governed by a particularlogical controller (e.g., logical controller 310). The logicalcontroller 310 of some embodiments translates the logical control planedata that defines the logical network into logical forwarding planedata, and the logical forwarding plane data into universal control planedata. Logical forwarding plane data, in some embodiments, consists offlow entries described at a logical level. For the MAC address A atlogical port X, logical forwarding plane data might include a flow entryspecifying that if the destination of a packet matches MAC A, forwardthe packet to port X. The port of the logical service node Q will alsohave a MAC address, and similar flow entries are created for forwardingpackets to port Y. In addition, some embodiments include flow entriesfor sending broadcast packets to several ports, which includes port Q.As such, DHCP packets that are sent as broadcast packets will reach thecorrect port.

The universal physical control plane of some embodiments is a data planethat enables the control system of some embodiments to scale even whenit contains a large number of managed forwarding elements (e.g.,thousands) to implement a logical data path set. The universal physicalcontrol plane abstracts common characteristics of different managedforwarding elements in order to express physical control plane datawithout considering differences in the managed forwarding elementsand/or location specifics of the managed forwarding elements.

As stated, the logical controller 310 of some embodiments translateslogical control plane data into logical forwarding plane data (e.g.,logical flow entries), then translates the logical forwarding plane datainto universal control plane data. In some embodiments, the logicalcontroller application stack includes a control application forperforming the first translation and a virtualization application forperforming the second translation. Both of these applications, in someembodiments, use a rules engine for mapping a first set of tables into asecond set of tables. That is, the different data planes are representedas tables (e.g., nLog tables), and the controller applications use atable mapping engine (e.g., an nLog engine) to translate between thedata planes. The input and output tables, in some embodiments, storesets of data tuples that define the data planes.

Each of the physical controllers 315 and 320 is a master of one or moremanaged forwarding elements (e.g., located within host machines). Inthis example, each of the two physical controllers is a master of twomanaged forwarding elements located at the host machines. Furthermore,the physical controller 315 is the master of the two logical servicenode hosts 345 and 350, which host the active and standby logicalservice nodes (with DHCP service) for a particular logical network(e.g., logical network 100). In some embodiments, the active and standbyhosts for a logical service node are managed by the same physicalcontroller (as in this figure), while in other embodiments separatephysical controllers managed the hosts.

In some embodiments, a physical controller receives the universalphysical control plane information for a logical network and translatesthis data into customized physical control plane information for theparticular managed forwarding elements that the physical controllermanages. In other embodiments, the physical controller passes theappropriate universal physical control plane data to the managedforwarding element, which has the ability (e.g., in the form of achassis controller running on the host machine) to perform theconversion itself.

The universal physical control plane to customized physical controlplane translation involves a customization of various data in the flowentries. For the example noted above, the universal physical controlplane would involve several flow entries. The first entry states that ifa packet matches the particular logical data path set (e.g., based onthe packet being received at a particular logical ingress port), and thedestination address matches MAC A, then forward the packet to logicalport X. This flow entry will be the same in the universal and customizedphysical control planes, in some embodiments. Additional flows aregenerated to match a physical ingress port (e.g., a virtual interface ofthe host machine) to the logical ingress port X (for packets receivedfrom MAC A, as well as to match logical port X to the particular egressport of the physical managed switch. However, these physical ingress andegress ports are specific to the host machine containing the managedswitching element. As such, the universal physical control plane entriesinclude abstract physical ports while the customized physical controlplane entries include the actual physical ports involved.

In some embodiments, as shown, the logical service node hosts 345 and350 also operate managed forwarding elements (e.g., using the samepacket processing software as the hosts 325-340). These MFEs alsoreceive physical control plane data from the physical controller thatenables the MFEs to implement the logical forwarding elements. Inaddition, some embodiments distribute the DHCP configuration data to thelogical service node hosts through the hierarchical network controlsystem. The logical controller 310 that manages the logical networkcontaining a logical service node selects the active and standby hostsfor the logical service node (e.g., using a load balancing algorithmthat spreads the logical service nodes for various logical networksacross a set of hosts).

The logical controller identifies the physical controller(s) thatmanages each of these selected LSN hosts, and distributes theconfiguration to the identified physical controllers. In someembodiments, the configuration is distributed as a set of data tuples.The physical controllers then distribute these data tuples to the LSNhosts. Both the active and standby hosts receive the same DHCPconfiguration, in some embodiments. As described in detail below inSection II, the LSN hosts convert these data tuples into a configurationreadable by the DHCP module that operates on the host.

The above describes the hierarchical controller cluster of someembodiments, although the network control system of other embodimentsincludes only a single controller (or controller cluster with one activeand one or more backup controllers). FIG. 4 conceptually illustrates thepropagation of data through the hierarchical network control system ofsome embodiments. The left side of this figure shows the data flow tothe managed forwarding elements to implement the logical forwardingelements of the logical network, while the right side of the figureshows the propagation of DHCP configuration data to the LSN hosts inorder to setup and configure the DHCP service for the logical network.

On the left side, the input translation controller 305 receives anetwork configuration through an API, which is converted into logicalcontrol plane data. This network configuration data includes a logicaltopology such as that shown in FIG. 1. The network configurationspecifies attachments of logical switches to logical service nodes insome embodiments, with MAC and IP addresses assigned to each logicalservice node port that connects to a logical switch.

As shown, the logical control plane data is converted by the logicalcontroller 310 (specifically, by a control application of the logicalcontroller) to logical forwarding plane data, and then subsequently (bya virtualization application of the logical controller) to universalphysical control plane data. In some embodiments, these conversionsgenerate a flow entry (at the logical forwarding plane), then add amatch over the logical data path set (at the universal physical controlplane). The universal physical control plane also includes additionalflow entries for mapping generic physical ingress ports (i.e., a genericabstraction of a port not specific to any particular physical hostmachine) to logical ingress ports as well as for mapping logical egressports to generic physical egress ports. For instance, for the mapping toa logical service node port, the flow entries at the universal physicalcontrol plane would include a forwarding decision to send a packet tothe logical port to which the logical service node connects when thedestination MAC address of the packet matches that of the logicalservice node port. In addition, the universal physical control planeentries would include a mapping of the logical port to a genericphysical port of a host machine that connects to the LSN host on whichthe logical service node resides, and generic tunneling entries forencapsulating the packet in a tunnel to the LSN host with the activelogical service node.

The physical controller 315 (one of the several physical controllers),as shown, translates the universal physical control plane data intocustomized physical control plane data for the particular managedforwarding elements that it manages at hosts 325, 330, 345, and 350.This conversion involves substituting specific data (e.g., specificphysical ports) for the generic abstractions in the universal physicalcontrol plane data. For instance, in the example of the above paragraph,the port integration entries are configured to specify the physicallayer port appropriate for the particular logical service nodeconnection (i.e., an actual physical port of the particular host machineon which the managed switching element operates).

The managed forwarding element at host 325 (one of several MFEs managedby the physical controller 315) performs a translation of the customizedphysical control plane data into physical forwarding plane data. Thephysical forwarding plane data, in some embodiments, are the flowentries stored within a switching element (either a physical router orswitch or a software switching element) against which the switchingelement actually matches received packets. In addition, the MFEs at bothof the logical service node hosts 345 and 350 perform such a translationin order to forward packets between the logical service nodes and theother network entities (e.g., VMs).

The right side of FIG. 4 illustrates data propagated to the logicalservice node hosts (e.g., host 345) to implement a DHCP service for alogical network, rather than to the MFEs. As shown, the inputtranslation controller receives a DHCP configuration input. The networkcontrol system may receive this data along with the logical networkconfiguration or as a separate set of inputs. For instance, anadministrator might create a logical service node in a logical network,but then enter a DHCP configuration at a later time. In addition, theDHCP configuration may be modified by an administrator while the systemis running. In some embodiments, the data flow illustrated in FIG. 4 isperformed by the network control system each time a logical service nodeis created, an attachment between a logical service node and a logicalswitch is created or removed, a DHCP service is added or removed from alogical service node, or a DHCP service is modified, among otheractions. As shown, the DHCP configuration input is translated by theinput translation controller into a DHCP configuration that the networkcontrol system can convert into data tuples.

The logical controller 310 is responsible for generating a set of datatuples that describe the DHCP configuration. For instance, when alogical service node is created, the logical controller of someembodiments selects an active LSN host and a standby LSN host, thencreates a new data tuple (i.e., a record) that specifies the existenceof a new namespace (or other container) on the host. If DHCP is enabled,some embodiments modify a value of this record, or create a differentrecord, indicating that a DHCP module should operate in the namespace.

Similarly, for each VM or other machine added to the DHCP service, thelogical controller generates a record that stores the MAC address, IPaddress, any DHCP options, and an associated port, or interface. Becausea logical service node may provide DHCP service for multiple differentlogical switches, each VM record is associated with the interface towhich the VM's logical switch connects. This enables the DHCP service touse the correct records when receiving DHCP requests.

In addition, records are created to store information for each logicalswitch. Specifically, DHCP options may be configured to apply to allhosts on a logical switch. These records, in some embodiments, associatean interface (i.e., the interface of the logical services node to whichthe logical switch connects) with the associated DHCP options for thelogical switch. Similarly, some embodiments create records to store DHCPoptions that should be applied globally, to all VMs (or other machines)connected to logical switches attached to the logical service nodes.

Once the logical controller 310 creates the data tuples and identifiesthe LSN hosts that will receive the data tuples, the logical controllerthen identifies the physical controller or controllers that manage theLSN hosts. As mentioned, like the VM hosts 325-340, each of the LSNhosts has an assigned master physical controller. In the example of FIG.3, both of the LSN hosts are managed by the physical controller 315, sothe other physical controller 320 does not receive the DHCP data tuples.

In order to supply the DHCP configuration data to the LSN hosts, thelogical controller 310 of some embodiments pushes the data (using anexport module that accesses the output of the table mapping engine inthe logical controller) to the physical controller 315. In otherembodiments, the physical controllers request configuration data (e.g.,in response to a signal that the configuration data is available) fromthe export module of the logical controller.

The physical controller 315 passes the data to the LSN hosts, including330, much as they pass the physical control plane data. In someembodiments, the DHCP configuration and the physical control plane datafor the MFE are sent to the same database running on the LSN hostmachine, and the MFE and namespace implementing the LSN retrieve theappropriate information from the database (or have the appropriateinformation passed to them).

In some embodiments, a process on the LSN host 345 translates the datatuples into a DHCP configuration file readable by the DHCP moduleoperating within the namespace. In some embodiments, this configurationfile is a text file with meta-language defining the DHCP service. Foreach logical switch, the configuration file defines a subnet, and thendefines the MAC to IP bindings and DHCP options for each machine in thesubnet. The configuration file generation of some embodiments isdescribed in further detail below in Section II.

FIG. 5 conceptually illustrates a process 500 performed by the logicalcontroller in some embodiments to assign a newly created DHCP serviceand its corresponding logical service node to a set of host machines. Inother embodiments that use a single controller, or single mastercontroller with one or more backups, the single controller performsprocess 500.

As shown, the process 500 begins by receiving (at 505) instructions tocreate a logical DHCP service. These instructions, in some embodiments,are received through an API as a combination of (i) instructions tocreate a new logical service node, (ii) instructions to create a port onthe logical service node to which a logical switch will attach, and (ii)instructions to enable a DHCP service for the port. In some cases, auser might create a logical network that includes a logical service nodewith one or more ports attached to logical switches, but not yet activeDHCP service on the logical service node. At a later time, the userwould then activate the DHCP service. The attachment of the logicalswitch to the port, in some embodiments, may also be received throughthe API and handled by the logical controller in order to generate flowentries for sending packets to the logical service node.

The process 500 then selects (at 510) one or more host machines for thelogical DHCP service (i.e., for the logical service node that offers theDHCP service). As mentioned, in some embodiments the logical controllerload balances the logical service nodes across a cluster of hostmachines designated for hosting logical service nodes. These hostmachines, in some embodiments, are of the same type as the VM hosts orL3 gateway service hosts (e.g., x86 boxes), but designated as a clusterfor logical service nodes.

Different logical controllers may run different load balancingalgorithms in some embodiments. When each logical service node iscreated as a namespace on two such host machines (i.e., one master andone backup), some embodiments attempt to operate as close to the samenumber of namespaces on each host machine as possible. In addition, someembodiments try to have an equal number of master and backup logicalservice nodes on a given host machine, so as to minimize the number ofmaster logical service nodes on any one machine in case of a failure andsubsequent failover. In addition, the master logical service nodesreceive substantially more traffic, and therefore require moreresources, than the backup logical service nodes. Other embodimentsfactor in the number of services offered, number of VMs (or othermachines) that access the services provided by a logical service node,actual traffic received/sent by the logical service node, and otherfactors in determining how to load balance the logical service nodesacross a cluster.

FIG. 6 conceptually illustrates a service host cluster 600 that includesfour host machines 605-620. As shown, three logical service nodes havebeen created on this cluster, with two instances (one master and onebackup) for each. The first host 605 hosts the master for LSN 1, thesecond host 610 hosts the backup for LSN 1 and the master for LSN 2, thethird host 615 hosts the backup for LSN 2 and the master for LSN 3, andthe fourth host 620 hosts the backup for LSN 3. If the controllercluster that manages this service host cluster 600 receives instructionsto create a new logical service node, some embodiments would place themaster for this new LSN 4 on the host machine 620 and the backup on host605. However, if LSN 1 was especially computationally intensive (e.g.,because it provides several services for numerous logical switches withmany connected VMs), while LSN 2 and LSN 3 have fewer connected VMs andare not as computationally intensive, some embodiments would locate thebackup for the new LSN 4 on, e.g., host 615.

Returning to the process 500, after selecting the one or more hostmachines for the logical service node, the process then creates (at 515)data tuples to define the DHCP service on the selected host machines.For instance, in some embodiments the network controller creates a datatuple to define a container (e.g., namespace). The data tuple'sexistence defines the existence of the namespace, and various other datain the tuple may define the configuration of the namespace. As anexample, a flag for enabling DHCP service can be set to either true orfalse in the data tuple of some embodiments, and global DHCP options(i.e., options to apply to all hosts that use the logical service nodeDHCP service) may be set in the data tuple for the namespace. Inaddition, other services (e.g., metadata proxy, DNS, etc.) may beenabled or disabled through this data tuple. In some embodiments, thenetwork control system also uses namespaces for logical routers, butturns off IP forwarding for logical service node namespaces. When a userhas already created a logical service node (which is already implementedin a namespace), but later turns on DHCP service for the logical servicenode, the controller modifies the data tuple for the already-creatednamespace to enable this DHCP service.

After generating the data tuples (or modifying previously created datatuples), the process 500 distributes (at 520) the created tuples to theselected host machines. As described above, in some embodiments thelogical controller distributes the data tuples to the physicalcontrollers that manage the selected host machines (through either apush or pull mechanism). These physical controllers subsequentlydistribute the data tuples to the host machines in order for the hostmachines to instantiate a namespace and/or a DHCP process within thenamespace.

FIG. 7 conceptually illustrates a process 700 performed by the logicalcontroller in some embodiments to configure a DHCP service for a logicalservice node. In other embodiments that use a single controller, orsingle master controller with one or more backups, the single controllerperforms the process 700.

As shown, the process 700 begins by receiving (at 705) a configurationfor a DHCP service for a logical service node. As with the instructionsto create a DHCP service, some embodiments receive this configurationthrough an API. The configuration may include settings for specificports (i.e., settings that apply to all VMs or other hosts associatedwith a particular port of the logical service node). As each of theports corresponds to a logical switch, the settings for the interfaceapply to all VMs that connect to the logical switch attached to theinterface. These settings may include values for DHCP options to applyto all VMs on the logical switch (e.g., specific static routes). Theconfiguration may also include a set of MAC to IP bindings for aparticular interface. That is, for MAC addresses requesting an IPaddress through a particular interface of the logical service node, theconfiguration provides the IP address that should be offered. Inaddition, the configuration may include a set of DHCP options and theirvalues for each host.

The process 700 then creates (at 710) data tuples for the receivedconfiguration. Some embodiments create a data tuple for each interfaceof the logical service node that uses the DHCP service. This data tuple,in some embodiments, maps the interface to the set of DHCP options forthe logical switch attached to the interface. In addition, someembodiments create a data tuple for each VM or other host. The VMconfiguration data tuple for the DHCP service includes a MAC address forthe VM, an IP address for the VM, a set of DHCP options, and theinterface of the logical service node that will receive DHCP requestsfrom the VM. In some embodiments, the DHCP options, whether global, perlogical switch, or per VM are expressed as key-value pairs in the datatuple. The key is the DHCP option, with a corresponding value for thatoption.

In some cases, a user may modify a previously created DHCPconfiguration. This may entail adding or removing a logical switchattachment (i.e., adding or removing an interface from the logicalservice node), adding or removing hosts, modifying IP addresses or DHCPoptions for hosts, etc. In this case, some embodiments modify theexisting data tuples, which the logical controller stores.

After generating the data tuples (or modifying previously created datatuples), the process 700 distributes (at 715) the created tuples to thehost machines on which the logical service node is active. In someembodiments, the logical controller stores a mapping of logical servicenodes to host machines, along with other network topology information.Using this information, the logical service node identifies the physicalcontroller or controllers that manages the host machines where both themaster and backup logical service nodes reside, and distributes the datatuples to these physical controllers (through either a push or pullmechanism). These physical controllers subsequently distribute the datatuples to the host machines in order for the host machines to generate aconfiguration for the DHCP service.

II. Generation of DHCP Configuration on Host

The above section described in detail the receipt of DHCP (and logicalservice node) configuration data by a controller, and the distributionof that data to the host machines on which the logical service nodesreside (e.g., as namespaces). In some embodiments, the host machineincludes various modules (e.g., running as daemons) that are responsiblefor creating the namespaces, activating DHCP and other services in thenamespace, and generating configuration files for the DHCP service,based on the data tuples distributed by the network control system.

FIG. 8 conceptually illustrates a software architecture of someembodiments for a host 800. The host 800 is a host designated forhosting logical service node implementations as namespaces. As shown,the host 800 includes virtualization software 805, two namespaces 810and 815, and a file system 820. In some embodiments, the host includes abase Linux operating system in which the namespaces 810 and 815 run ascontainers, and the file system 820 is the file system associated withthis base operating system.

The virtualization software 805 includes a virtual switch daemon 825, avirtual switch database daemon 830, a namespace daemon 835, and avirtual switch kernel module 840. In some embodiments, the virtualswitch daemon, the virtual switch database daemon 830, and the namespacedaemon 835 operate in the user space of virtualization software 805,while the virtual switch kernel module 840 operates in the kernel of thevirtualization software 805. In some embodiments, the virtual switchused on the host is Open Vswitch (OVS), and these modules are the OVSdaemon, OVS DB daemon, and OVS kernel module, in addition to thenamespace daemon. One of ordinary skill in the art will recognize that,in addition to the modules shown, which relate to the virtual switch andhosted namespaces, the virtualization software of some embodimentsincludes additional modules for performing, e.g., virtualization of thehardware resources (e.g., processors, memory, etc.) of the host machine800.

The virtual switch daemon 825 is an application that communicates with aphysical network controller 895 in some embodiments in order to receiveinstructions for processing and forwarding packets sent to and from thenamespaces 810 and 815. Specifically, as described in the previoussection, the virtual switch daemon 825 receives physical control planeflow entries from the physical controller 895. The virtual switchdaemon, in some embodiments, communicates with the network controllerthrough the OpenFlow protocol, though other embodiments may usedifferent communication protocols for transferring the forwarding data.Additionally, in some embodiments the virtual switch daemon 825retrieves configuration information from the virtual switch databasedaemon 830 after the physical controller 895 transmits the configurationinformation to the virtual switch database daemon.

The virtual switch daemon 825 of some embodiments includes a flowprotocol module 850 and a flow processor 855. The flow protocol module850 handles the communication with the network controller 895 in orderto receive physical control plane information (e.g., flow entries) forthe virtual switch. As mentioned, in some embodiments this communicationuses the OpenFlow protocol. When the flow protocol module 850 receivesthis physical control plane information, it translates the receivedinformation into data understandable by the flow processor 855 (e.g.,physical forwarding plane information useable for processing packets).

The flow processor 855 manages the rules for processing and forwarding(i.e., switching, routing) packets in some embodiments. For instance,the flow processor 855 stores rules (e.g., in a storage medium, such asa disk drive) received from the flow protocol module 850. In someembodiments, the rules are stored as a set of flow tables that eachincludes a set of flow entries. These flow entries, in some embodiments,include a match (i.e., a set of packet characteristics) and one or moreactions (i.e., a set of actions to take on packets that match the set ofcharacteristics). In some embodiments, the flow processor 825 handlespackets for which the managed bridge 860 (described below) does not havea matching rule. In such cases, the flow processor 855 matches thepackets against its stored rules. When a packet matches a rule, the flowprocessor 825 sends the matched rule and the packet to the managedbridge 860 for the managed bridge to process. This way, when the managedbridge 860 subsequently receives a similar packet that matches thegenerated rule, the packet will be matched against the generated exactmatch rule in the managed bridge and the flow processor 855 will nothave to process the packet.

In some embodiments, the virtual switch database daemon 830 is anapplication that also communicates with the physical controller 895 inorder to configure the virtual switching element (e.g., the virtualswitch daemon 825 and/or the virtual switch kernel module 840). Forinstance, the virtual switch database daemon 830 receives configurationinformation from the physical controller and stores the configurationinformation in a set of database tables 845. This configurationinformation may include tunnel information for creating tunnels to othermanaged forwarding elements, port information, etc. In some embodiments,the virtual switch database daemon 830 communicates with the networkcontroller 895 through a database communication protocol. In some cases,the virtual switch database daemon 830 may receive requests forconfiguration information from the virtual switch daemon 825. Thedatabase daemon 830, in these cases, retrieves the requestedconfiguration information (e.g., from its set of database tables 845)and sends the configuration information to the virtual switch daemon825.

As shown, the virtual switch database daemon 830 includes aconfiguration retriever 865 and a set of database tables 845 (which maybe stored, e.g., on a hard drive or other storage of the host 800). Theconfiguration retriever 865 is responsible for communications with thephysical controller 895. In some embodiments, the configurationretriever receives the configuration information for the virtual switchfrom the controller. In addition, the configuration retriever in someembodiments receives the data tuples describing the logical service nodeand DHCP configuration. The configuration retriever 865 also convertsthese data tuples into database table records to store in the databasetables 845.

Specifically, the database tables 845 of some embodiments include acontainer table, with each record in the database defining a differentnamespace (or other container) on the host machine. Thus, for the host800, the container table would include a row for each of the twonamespaces 810 and 815. In some embodiments, these rows each includecolumns for DHCP options to apply globally within the DHCP service, aswell as a configuration column that stores the enable/disable status ofvarious services that may exist in the namespace (e.g., DHCP, metadataproxy, etc.). When the configuration retriever 865 receives a modifieddata tuple indicating that the DHCP service should be enabled for aparticular logical service node, the configuration retriever modifiesthe database tables 845 to set the DHCP enabled status to true for thenamespace that implements the logical service node.

The database tables 845, in some embodiments, also include a table foreach logical switch, which may be treated as a subnet (as the DHCPmodule may not be aware of the concept of a logical switch). Eachinterface of a logical service node is assigned a row in the databasetables, which stores the DHCP options (as key-value pairs) and theinterface ID to which these options apply. In addition, the databasetables 845 of some embodiments include a table that stores theconfiguration for the VMs or other entities (e.g., physical hosts)serviced by the DHCP service. This table includes a row for each VM orother host, with each row including (i) the MAC address of the VM/host(ii) the IP address assigned to the VM/host, (iii) the DHCP options(again as key-value pairs) to apply to the VM/host, and the interfacethrough which the logical service node (and therefore the DHCP service)receives requests from the VM/host. Because the table includes a columnfor the interface, a single table can store information for all of thehosts serviced by a particular logical service node, even if those hostsare on multiple different logical switches (and therefore assigned todifferent interfaces).

The virtual switch kernel module 840 processes and forwards network data(e.g., packets) between the namespaces running on the host 800 andnetwork hosts external to the host 800 (e.g., network data receivedthrough the NIC 870). In some embodiments, the virtual switch kernelmodule 840 implements the forwarding tables of the physical controlplane for one or more logical networks (specifically, the logicalnetworks to which the namespaces 810 and 815 belong). To facilitate theprocessing of network data, the virtual switch kernel module 840communicates with virtual switch daemon 825 (e.g., to receive flowentries from the flow processor 855).

FIG. 8 illustrates that the virtual switch kernel module 845 includes amanaged bridge 860. In addition, in some embodiments, the virtual switchkernel module may include additional bridges, such as an integrationbridge and physical interface (PIF) bridges. Some embodiments include aPIF bridge for each NIC 870 in the host machine's hardware. In thiscase, in some embodiments a PIF bridge is located between the managedbridge 860 and the NIC 870.

The managed bridge 860 of some embodiments performs the actualprocessing and forwarding of the packets between the namespaces 810 and815 and the VMs and other hosts that communicate with the namespaces.Packets are received at the managed bridge 860 from the external sourcesthrough tunnel ports, such that packets arriving over different tunnelsare received at different interfaces of the bridge 860. Based on thedestination logical port appended to the packet (or other information,such as a destination MAC or IP address, etc.), the managed bridge 860sends the packet to the appropriate namespace through its interface withthe namespace. Similarly, the managed bridge receives packets from thenamespaces 810 and 815, and processes and forwards these packets usingthe interface through which the packets are received and destinationaddresses of the packets. In some embodiments, to process the packets,the managed bridge 860 stores a subset of the rules stored in the flowprocessor 855 (and/or rules derived from rules stored in the flowprocessor 855) that are in current or recent use for processing thepackets.

Although FIG. 8 illustrates one managed bridge, the virtual switchkernel module 840 may include multiple managed bridges. For instance, insome embodiments, the virtual switch kernel module 840 includes aseparate bridge for each logical network that is implemented within thehost machine 800, or for each namespace residing in the host (which willoften be the same as each logical network).

Each of the namespaces 810 and 815 implements a different logicalservice node. The namespaces may be an active or a standbyimplementation of their logical service node, although in someembodiments the namespace is not aware of its status as active orstandby. As described below, the tunnels on the VM hosts are managedsuch that packets will always be sent to the active logical service nodeimplementation. As such, the standby implementations operate as thoughactive, but should not receive any traffic. As indicated in this figure,different namespaces implementing different logical service nodes fordifferent logical networks (or for the same logical network) may resideon the same host 800 in some embodiments. As a result, different DHCPserver instances providing DHCP service for different logical networksmay reside on the same host 800.

The logical service nodes may provide multiple services. In this case,both of the namespaces 810 and 815 include DHCP modules 875 and 880,respectively, as well as other services 885 and 890. In someembodiments, the DHCP modules 875 and 880 are instances of a commonlyavailable DHCP server, such as Linux's dhcp daemon (dhcpd). Otherembodiments use different DHCP modules to provide DHCP service withinthe namespace. The other services 885 and 890 may differ between twonamespaces. For example, one of the logical service nodes might beconfigured to provide metadata proxy, while the other logical servicenode is configured to provide DNS. In addition, some embodiments provideDHCP relay service, though some such embodiments do not allow DHCP relayservice and DHCP service in the same logical service node.

The DHCP modules 875 and 880 provide DHCP service according to definedconfigurations. As described below, in some embodiments the namespacedaemon 835 generates configuration files 892 for these modules andstores the configuration files in the host file system 820 (e.g., in apre-specified directory of the file system). The DHCP modules 875 and880 access their respective configuration files in order to processincoming DHCP requests from VMs and other hosts that they service.

The namespace daemon 835 of some embodiments manages the namespaces 810and 815 residing on the host 800 and the services running in thosenamespaces (e.g., DHCP service). As shown, the namespace daemon 835includes a virtual switch database monitor 894 and a DHCP configurationgenerator 897. In addition, some embodiments include configurationgenerators or similar modules for other services (e.g., a metadata proxyconfiguration generator).

The virtual switch database monitor 894 listens on the database tables845 for changes to specific tables that affect the namespacesimplementing logical service nodes. These changes may include thecreation of a new namespace, removal of a namespace, enabling a newservice within a particular namespace, creating or modifying a DHCPconfiguration (or other service configuration), etc. When the virtualswitch database monitor 894 detects a change that affects thenamespaces, it either causes the namespace daemon to create a newnamespace on the host for a new logical service node, instantiate aprocess in an existing namespace for a newly enabled service, orgenerate/modify a configuration file for an existing service.

When DHCP configuration data is retrieved by the monitor 894, the DHCPconfiguration generator 897 generates or modifies a configuration filefor the DHCP process. To generate a configuration file, the DHCPconfiguration generator stores methods for parsing the retrieveddatabase tables 845 and writing this information to a file in a formatreadable by the DHCP module. In some embodiments, the configurationgenerator 897 writes data to a text file in a meta language. This textfile contains MAC address to IP address bindings (i.e., for VMs or otherhosts), subnet (i.e., logical switch)-specific settings, globalsettings, etc. For instance, although the database tables are defined interms of interfaces that correspond to logical switches in someembodiments, the DHCP module may have no conception of either thelogical interface of the logical service node or of the logical switch.Accordingly, some embodiments treat each logical switch as an IP subnet,a format readable by the DHCP module.

In addition, some of the specified DHCP options may not be supported bythe DHCP modules 875 and 880. For an unsupported specified option, someembodiments use a predetermined formula to write a series of statements(e.g., a combination of supported options) into the configuration filein order to arrive at the functional equivalent of the specified option.For supported options, the DHCP configuration generator 897 writes theoption and its value into the configuration file associated with thecorrect entity (a subnet, a particular MAC address, etc.). Theconfiguration generator of some embodiments will be described in furtherdetail below by reference to FIG. 11.

After generating a new configuration file, the namespace daemon 835 ofsome embodiments stores the configuration file in the file system 820,possibly overwriting an existing configuration file for the DHCP module.In addition, after changes to the configuration file, some embodimentsissue a command to restart the DHCP module, thereby allowing the moduleto pick up the new configuration. In addition, for smaller changes tothe DHCP configuration, some embodiments use a different method todirectly modify the configuration of the running DHCP module, that doesnot require a restart.

Certain operations of the namespace daemon 835 will now be described byreference to FIGS. 9 and 10. FIG. 9 conceptually illustrates a process900 of some embodiments for starting up a new DHCP service on a LSN host(e.g., the host 800). As shown, the process 900 begins by receiving (at905) database tables (or table records) creating a new DHCP service torun on a host machine. As described above, the namespace daemon maylisten for changes to certain database tables stored on the host, inorder to identify actions it needs to take regarding the DHCP processes,including creating or removing namespaces, instantiating DHCP processes,modifying configuration files, etc.

The process 900 determines (at 910) whether the container for the DHCPservice is yet operating on the host machine. When the modified databasetables include a new row for a new namespace that contains the enabledDHCP service, then the container will not yet be operating. In thiscase, the process creates (at 915) a container for the DHCP service onthe host machine. As indicated, in some embodiments this container is anamespace, which is a lightweight (less computationally intensive)container (e.g., as compared to a virtual machine). Like VMs, namespacesare virtualizations that can share virtualized hardware resources withother virtualization (e.g., other namespaces, VMs).

After the container is created, or if the container has already beencreated, the process 900 starts (at 920) the DHCP service in thecontainer. This may involve the namespace daemon sending a command tothe namespace to instantiate a DHCP module (e.g., dhcpd). This causesthe DHCP module to start, but without a configuration, the DHCP modulewill not actually provide any useful service.

The process next determines (at 925) whether a configuration is definedfor the DHCP service. This determination specifically identifies whetherdatabase tables defining any configuration for the DHCP service exist.In some embodiments, even if the user provides a configuration at thesame time as they initiate the logical network with the logical servicenode, the namespace daemon may receive the database tables defining theexistence of the logical service node before the configuration. When noconfiguration is yet defined for the DHCP service, the process ends.When a configuration is defined, the process 900 generates (at 930) aconfiguration file for the DHCP service from the database tables thatdefine the configuration, then ends. The generation of a configurationfile will be described in greater detail below by reference to FIGS. 11and 12.

This process 900 describes the operations of the namespace daemon ofsome embodiments to create a new DHCP service. One of ordinary skill inthe art will recognize that the virtual switch daemon and the virtualswitch kernel module, in some embodiments, also perform operations inorder to create the forwarding tables used to forward packets to andfrom the newly created namespace.

FIG. 10 conceptually illustrates a process 1000 of some embodiments formodifying an existing DHCP configuration of an operating DHCP module. Insome embodiments, the process 1000 is performed by a namespace daemon(e.g., daemon 835) to modify a DHCP configuration for a module operatingin a namespace (e.g., DHCP module 875). As shown, the process begins (at1005) by receiving (at 1005) database tables (or table records) thatmodify an operational DHCP service configuration. As described above,the namespace daemon may listen for changes to certain database tablesstored on the host, in order to identify actions it needs to takeregarding the DHCP processes. This includes identifying modifications toexisting tables and existing table records that modify the configurationfor a DHCP service.

The process 1000 determines (at 1010) whether the identified changesrequire a restart of the DHCP service. In effect, this is adetermination as to whether the changes can be made at runtime. In someembodiments, whether to perform changes at runtime requires a decisionby the developer (e.g., of the namespace daemon). As making changes atruntime is more convenient but requires significantly more developmenttime, some embodiments perform smaller, more common changes by directlyaccessing the running DHCP module and modifying its configuration atruntime. However, for larger and less common changes the namespacedaemon modifies the configuration file and then restarts the DHCPmodule.

When the changes do not require a restart, the process uses (at 1015) aruntime configuration protocol to modify the DHCP service configuration,then ends. In some embodiments, the namespace daemon uses ObjectManagement API (OMAPI), which allows for the manipulation of an internaldata structure of certain DHCP servers (e.g., dhcpd), to make runtimechanges to the DHCP module. As mentioned, some embodiments only makesmaller changes to the DHCP configuration at runtime. In someembodiments, these changes include the addition, modification, orremoval of individual VMs or other hosts (e.g., an addition, removal, ormodification of an entry in the host database table). Modification tothe settings for a VM could include the modification of its IP address,or changing the DHCP options for the VM. In addition to directlymodifying the running service, some embodiments also modify theconfiguration file in order to keep the file up to date (e.g., in caseof a crash and necessary restart).

On the other hand, when the changes can not be performed at runtime andtherefore require a restart of the DHCP service, the process 1000 edits(at 1020) the configuration file for the DHCP service and restarts (at1025) the service. After restarting the service, the process ends. Insome embodiments, the namespace daemon makes larger and less commonchanges to the service offline. For instance, some embodiments modifythe configuration file, then restart, for any changes to global(service-wide) options or to options for a specific port of the DHCPservice (i.e., for all hosts of a specific logical switch). In addition,the addition or removal of a logical switch attachment to the DHCPservice requires a restart in some embodiments. One of ordinary skillwill recognize that the division between when to restart and when todirectly modify the configuration is a developer or administratorchoice, and can be modified in different embodiments. For example, someembodiments would not restart for modifications to per logical switchoptions, or would even perform all changes at runtime.

In some embodiments, when restarting, the namespace daemon for themaster logical service node coordinates with the namespace daemon forthe backup logical service node to ensure that both the master and thebackup are not both restarting at the same time. In other embodiments,the master and backup operate independently.

FIG. 8 above describes a host machine, which includes a DHCPconfiguration generator 897 that is part of the namespace daemon 835.The following FIG. 11 conceptually illustrates a namespace daemon 1100of some embodiments in greater detail. Specifically, this figuresillustrates in further detail the features of the DHCP configurationgenerator 897.

As shown, the namespace daemon 1100 includes a monitor 1105, restartdecision logic 1110, a configuration file generator 1115, and a runtimeconfiguration modifier 1117. In some embodiments, the restart decisionlogic 1110, configuration file generator 1115, and runtime configurationmodifier 1117 perform the functions of the DHCP configuration generator897. One of ordinary skill in the art will recognize that the namespacedaemon of some embodiments may include additional or different modules,such as configuration generators for other services besides DHCP.

The monitor 1105, as described above by reference to FIG. 8, monitorsthe database tables 1120 to identify changes to the DHCP configurationfor any logical service nodes operating as namespaces on the hostmachine. In some embodiments, the monitor additionally monitors tablesrelating to other services (e.g., metadata proxy). The database tables1120, in some embodiments, include tables that define each logicalservice node as a container (e.g., namespace 1130) and the servicesenabled in the container (e.g., DHCP, DNS, metadata proxy, etc.), thelogical switches that attach to the logical service node, MAC to IPbindings for the serviced VMs and other hosts, DHCP options (global, perlogical switch, and per VM options), etc. These database tables 1120 arestored in a specific format (e.g., OVSdb) in some embodiments. In someembodiments, this format is the same as that used for otherconfiguration data for the host machine, such as the managed forwardingelement configuration (e.g., port and tunnel information, etc.).

The monitor 1105, in some embodiments, periodically checks the databasetables 1120 for updates that affect the DHCP configuration. In otherembodiments, the monitor is automatically notified every time thedatabase tables are updated, and the monitor 1105 then queries thetables 1120 for updates.

The restart decision logic 1110 of some embodiments receivesconfiguration information (e.g., database table records identified bythe monitor 1105) for one of the DHCP services operating on the host(e.g., the DHCP module 1135) and determines whether to update the DHCPservice by using a runtime configuration protocol or by modifying theconfiguration file for the service and then restarting the service.Newly created namespaces or DHCP services will not use the runtimeconfiguration protocol. However, for modifications to existing DHCPservices, different embodiments have different breakdowns betweenchanges that require restarting the DHCP module and changes that can beperformed at runtime.

Some embodiments only make smaller changes to the DHCP configuration atruntime. In some embodiments, these changes include the addition,modification, or removal of individual VMs or other hosts (e.g., anaddition, removal, or modification of an entry in the host databasetable). Modification to the settings for a VM could include themodification of its IP address, or changing the DHCP options for the VM.

Some embodiments make larger changes to the running DHCP serviceoffline. For instance, some embodiments modify the configuration file,then restart the service, for any changes to global (service-wide)options or to options for a specific port of the DHCP service (i.e., forall hosts of a specific logical switch). Furthermore, the addition orremoval of a logical switch attachment to the DHCP service requires arestart in some embodiments. One of ordinary skill will recognize thatthe division between when to restart and when to directly modify theconfiguration is a developer or administrator choice, and can bemodified in different embodiments. For example, some embodiments wouldnot restart the service for modifications to per logical switch options.

When the restart decision logic 1110 determines that the changes requirerestarting the service, the restart decision logic sends the changes(e.g., the updated database table entries) to the configuration filegenerator 1115. On the other hand, when the restart decision logic 1110determines that the changes can be performed at runtime, it sends theseupdates to the runtime configuration modifier 1117. In some embodiments,the restart decision logic always sends the updates to the configurationfile generator 1115, which updates the configuration file even when norestart is required. With all changes to the DHCP configuration trackedin the configuration file, if the namespace or DHCP module crashes, theconfiguration file need not be updated before restarting. Furthermore,if additional updates are received that do require a restart, only thosenew updates will need to be edited into the configuration file.

The configuration file generator 1115 of some embodiments containsvarious logic for converting database table entries that describe a DHCPservice into the appropriate configuration file language ormeta-language for the DHCP module 1135. In some embodiments, differentDHCP modules use different configuration languages or even differenttypes of configuration files. In some embodiments, namespaces run thedhcpd application, which reads its configuration from a specificmeta-language written into a text file.

In this example, the configuration file generator 1115 includes logicalswitch to subnet logic 1140, MAC:IP bindings logic 1145, supportedoptions conversion logic 1150, and non-supported options conversionlogic 1155. One of ordinary skill in the art will recognize thatdifferent embodiments may perform various different or additionalconversions from database table entries to configuration file data. Thelogical switch to subnet logic 1140, in some embodiments, defines asubnet or group for a specific interface of the namespace. In someembodiments, logical switches each attach to a separate interface of thelogical service node implemented by a namespace, as shown in FIG. 1.However, many DHCP modules are not aware of the logical switch concept,and instead view them as subnets or groups. Therefore, for eachinterface defined as belonging to the particular namespace in a databasetable entry, some embodiments define a group, or subnet, in theconfiguration file.

The MAC:IP bindings logic 1145 of some embodiments defines each VM oneach logical switch serviced by a particular DHCP module (e.g., module1135). Each VM or other host belongs to a particular logical switch, forwhich a group/subnet has been defined in the configuration file. Thelogic 1145 of some embodiments defines each VM within the configuration,and declares the MAC address and IP address assigned to the VM (if bothare available) within the definition of the VM. For static DHCP, the IPaddress is declared as a fixed address in some embodiments.

The configuration file generator 1115 contains both supported optionsconversion logic 1150 and non-supported options conversion logic 1155.DHCP options are optional configuration parameters that may be providedto a DHCP client (i.e., a VM or other host). These options fall intovarious categories, such as various vendor extensions (which, e.g.,provide information about available servers of various types (DNSservers, time servers, etc.), available routers, domain names, etc.), IPlayer parameters (e.g., MTU size, default time to live, static routes,etc.), link layer and TCP parameters, application and service parameters(e.g., default servers for specific applications or protocols), and DHCPextensions (e.g., renewal time, lease time, etc.). In some embodiments,the DHCP options may be specified on a global basis (i.e., for allsubnets or groups), a per logical switch basis (i.e., for all hosts in aspecific subnet/group), or on a per host basis. RFC 2132, whichspecifies many of the DHCP options, is available athttp://tools.ietf.org/html/rfc2132, and is incorporated herein byreference.

In some embodiments, the DHCP module does not support all DHCP options.If a specified option is supported, then the configuration filegenerator 1115 uses supported options conversion logic 1150 to definethe specified option in the configuration file. When a supported DHCPoption is specified in the database table entry for a particular logicalservice node (and therefore a particular DHCP service), the conversionlogic 1150 defines the option globally in the configuration file. Thisoption will then be provided by the DHCP module to any VM requesting anIP address on any of the namespace interfaces. When a supported DHCPoption is specified in the database table entry for a particular logicalswitch, the conversion logic 1150 defines the option within thespecification of the group/subnet to which the particular logical switchcorresponds. This option will then be provided by the DHCP module to anyVM requesting an IP address on that particular interface. Finally, whena database table entry for a VM specifies a supported DHCP option, theconversion logic 1150 defines the option within the specification of theVM.

For an option not supported by the DHCP module (whether the option isdefined globally, for a specific logical switch, or for a specifichost), the non-supported option conversion logic 1155 stores a set ofoperations for converting the specified option to supported features. Insome embodiments, the process first defines the option as a new type ofoption within the configuration file and then writes into theconfiguration the specific value for the option. In some embodiments,one option may be written in terms of various supported options withvalues determined based on the value specified for the non-supportedfeature.

One example of an option that might not be supported in some embodimentsis the classless-static-routes option, which may be used to configure aVM routing table with static routes. For a DHCP module that does supportthis option, the configuration file might read “optionclassless-static-routes 192.168.35.0/24 10.20.0.1, which would instructthe VM to forward packets for 192.168.35.0/24 through the router at10.20.0.1.

However, some embodiments do not support this option, and thus theoption from the database tables is converted to first define “optionclassless-static-routes code 121=array of integer 8;”. This statementdefines a new option “classless-static-routes” that uses a code 121 andthe value of which is an array of 8 bytes. Next, the specific requestedoption is written into the configuration file as “optionclassless-static-routes=24, 192, 168, 35, 10, 20, 0, 1. Based on theDHCP option RFC that defines this option, the configuration fileinstructs the DHCP module to put these exact bytes into the packet asthe value of the option with code 121, which will be understood by thereceiving VM. Thus, for any option, the configuration file generatorfirst defines the option in the configuration file along with an optioncode, then defines for the DHCP module exactly how to specify thedesired value in a DHCP offer or acknowledgment packet.

The configuration file generator 1165 also includes a file systemaccessor 1160 and a DHCP service restarter 1165. The file systemaccessor 1160 enables the configuration file generator 1165 to accessthe host machine's file system, and stores the configuration filegenerated using the various conversion logic modules 1140-1155 to theappropriate directory in the file system. FIG. 12, described below,conceptually illustrates a process for generating a configuration file.

The DHCP service restarter 1165 is responsible for communicating withthe DHCP modules operating in the namespaces (e.g., module 1135 innamespace 1130) on the host machine in order to restart the DHCPmodules. When the DHCP application or daemon that implements the DHCPservice restarts, it reads in a configuration from a configuration filein a particular directory. Therefore, after the file system accessor1160 writes an updated configuration file for a particular DHCP serviceto the file system 1125 after larger changes to the configuration, therestarter 1165 effects a restart of the particular DHCP service.However, when the changes to the configuration file mirror those madedirectly to the running DHCP module through the runtime configurationmodifier 1117, then the restarter 1165 does not restart the DHCPservice.

When the runtime configuration modifier 1117 receives updates to a DHCPconfiguration, the configuration modifier directly modifies theconfiguration of the corresponding operating DHCP module (e.g., module1135). In some embodiments, the operating DHCP module instantiatesobjects for each group/subnet and for each host declared in theconfiguration file. The runtime configuration modifier 1117 of someembodiments modifies these objects (e.g., through the Object ManagementAPI (OMAPI)).

As with the configuration file generator 1115, the runtime configurationmodifier 1117 includes logical switch to subnet logic 1170, MAC:IPbindings logic 1175, supported options conversion logic 1180, andnon-supported options conversion logic 1185. Whereas the logic 1140-1155converts database table entries into configuration file meta-language,the logic 1170-1185 provides instructions to the DHCP module interface1190 as to how to modify the instantiated objects of the DHCP module1135. For instance, for embodiments that add or remove logical switchesthrough runtime modification, the logical switch to subnet logic 1170provides instructions regarding a group/subnet object to add or remove.The MAC:IP bindings logic 1175, in some embodiments, provideinstructions regarding host objects to modify, add, or remove.Similarly, the options logic 1180 and 1185 provides instructionsregarding the modification, addition, and removal of options from thegroup/subnet objects, the host objects, or the global definitions. TheDHCP module interface 1190 is responsible for communicating with theDHCP modules (e.g., module 1135) to modify the objects (e.g., usingOMAPI).

As mentioned, FIG. 12 conceptually illustrates a process 1200 of someembodiments for generating a configuration file for a DHCP module (e.g.,for dhcpd) based on a set of database table entries defining a DHCPconfiguration. While this process illustrates the generation of a newconfiguration file, one of ordinary skill will recognize that a similarprocess with similar operations would be performed to modify an existingconfiguration file. In some embodiments, the process is performed by anamespace daemon such as daemon 1100 (e.g., by the configuration filegenerator 1115 in response to the monitor 1105 identifying a new DHCPconfiguration).

The process 1200 begins (at 1205) by receiving a DHCP configuration as aset of database table entries. As described above, these database tableentries may include entries for the namespace itself (enabling DHCP in anamespace), entries for logical switches, and entries for VMs and otherhosts (which the DHCP service simply views as a host, irrespective ofwhether the host is a VM or other entity). Assuming DHCP is enabled fora particular namespace, the namespace daemon will generate aconfiguration file based on the other data for the DHCP service.

The process 1200 identifies (1210) logical switch information in thedatabase table entries, and writes (at 1215) the logical switchinformation into the configuration file (e.g., as a subnet or group). Insome embodiments, logical switches each attach to a separate interfaceof the logical service node implemented by a namespace, as shown inFIG. 1. However, many DHCP modules are not aware of the logical switchconcept, and instead view them as subnets or groups. Therefore, for eachinterface defined as belonging to the particular namespace in a databasetable entry, some embodiments define a group, or subnet, in theconfiguration file. Each group is defined as including a range of IPaddresses, in some embodiments.

Next, the process identifies (at 1220) VM or other host information inthe database table entries, and writes (at 1225) the VM information intothe configuration file (e.g., as hosts). Each VM or other host belongsto a particular logical switch, for which a group/subnet has beendefined in the configuration file. Some embodiments define each VMwithin the configuration, and declare the MAC address and IP addressassigned to the VM (if both are available) within the definition of theVM. For static DHCP, the IP address is declared as a fixed address insome embodiments.

The process 1200 also deals with writing the options into theconfiguration file. One of ordinary skill in the art will recognizethat, while shown separately from the logical switch and VM definitions,in some embodiments the configuration file generator converts theoptions for a particular logical switch as part of operation 1215, andthe options for a particular VM as part of operation 1225.

In this case, the process 1200 determines (at 1230) whether there areany DHCP options to write to the configuration file. These options fallinto various categories, such as various vendor extensions (which, e.g.,provide information about available servers of various types (DNSservers, time servers, etc.), available routers, domain names, etc.), IPlayer parameters (e.g., MTU size, default time to live, static routes,etc.), link layer and TCP parameters, application and service parameters(e.g., default servers for specific applications or protocols), and DHCPextensions (e.g., renewal time, lease time, etc.). In some embodiments,the DHCP options may be specified on a global basis (i.e., for allsubnets or groups), a per logical switch basis (i.e., for all hosts in aspecific subnet/group), or on a per host basis. When the configurationdoes not specify any options, the process ends.

When the configuration does specify at least one option, the process1200 selects (at 1235) one of the DHCP options. Some embodiments selectthe option based on the order in which the database table entries arereceived. In some embodiments, the namespace daemon first converts theglobal options, then the per logical switch options, then finally thehost-specific options. In some embodiments, the options are convertedand written into the configuration file along with their respectiveobject (e.g., a group or a host). When an option is specified in a rowthat defines a logical switch, the namespace daemon writes that optionto the configuration file while defining the logical switch as agroup/subnet.

With an option selected, the process determines (at 1240) whether theoption is supported by the DHCP module. When the option is supported,the process 1200 writes (at 1245) the option to the configuration file.When a supported DHCP option is specified in the database table entryfor a particular logical service node (and therefore a particular DHCPservice), the process defines the option globally in the configurationfile. This option will then be provided by the DHCP module to any VMrequesting an IP address on any of the namespace interfaces. When asupported DHCP option is specified in the database table entry for aparticular logical switch, the process defines the option within thespecification of the group/subnet to which the particular logical switchcorresponds. This option will then be provided by the DHCP module to anyVM requesting an IP address on that particular interface. Finally, whena database table entry for a VM specifies a supported DHCP option, theprocess defines the option within the specification of the VM.

When the option is not supported by the DHCP module, the process 1200retrieves (at 1250) a set of declarations for creating an equivalent tothat option, and writes (at 1255) the set of declarations to theconfiguration file. This set of declarations may include, e.g., variousother options that are supported by the DHCP module. In someembodiments, for any non-supported option, the configuration filegenerator first defines the option in the configuration file along withan option code, then defines for the DHCP module exactly how to specifythe desired value in a DHCP offer or acknowledgment packet.

After writing the option to the configuration file, the processdetermines (at 1260) whether any additional options remain to write tothe file. When additional options remain, the process returns to 1235 toselect another of the DHCP options. Otherwise, the process ends.

III. DHCP Processing

The previous sections describe the configuration of a DHCP service for alogical network, at both the controller level and the host machinelevel. Once the DHCP service is configured on one or more logicalservice node hosts, the various VMs that use that DHCP service canrequest IP addresses by sending DHCP requests to the LSN hosts.

In some embodiments, the DHCP implementation follows the standarddiscovery/offer/request/acknowledgement multi-stage process, in thelogical network. That is, the requesting VM first broadcasts a DHCPdiscovery message on its logical switch. The receiving DHCP server thenresponds by broadcasting a DHCP offer message that includes an offeredIP address. Upon receiving this offer, the VM broadcasts a DHCP request,which formally requests the IP address offered by the DHCP server.Lastly, the DHCP server broadcasts an acknowledgment that the IP addresshas been assigned to that VM.

In traditional networks, DHCP is a broadcast protocol, and several DHCPservers (in addition to other machines on the network) may receive eachmessage (as the messages are all sent as broadcast packets). In someembodiments, the logical networks preserve this broadcast feature, suchthat the messages are broadcast to all ports of the logical switch onwhich the requesting VM resides.

FIG. 13 conceptually illustrates a process 1300 of some embodimentsperformed by a DHCP service in a logical network (e.g., the DHCP module875 or 880 from FIG. 8. The DHCP service operates in a namespace orother container that implements a logical service node in someembodiments, as explained in the above sections. The process 1300 willbe described in part by reference to FIG. 14, which illustrates alogical network 1400, its implementation in a physical network, and aDHCP discovery packet sent by one of the VMs of the logical network.

As shown, the process 1300 begins by receiving (at 1305) a DHCPdiscovery packet from a particular port of the container on which theDHCP module operates. A logical service node with DHCP enabled may serveseveral different logical switches in some embodiments, and each logicalswitch attaches to a different port of the logical service node. In someembodiments, each of these ports is assigned a different MAC address andIP prefix (e.g., corresponding to the IP prefix used for the VMs on thelogical switch to which it attaches). The DHCP module receives a DHCPdiscovery packet through one of these ports, and for subsequentmessages, the traffic is sent through this port.

FIG. 14 conceptually illustrates a VM sending a DHCP discovery messageonto an implementation of a logical network 1400. As shown, the logicalnetwork 1400 includes a logical switch 1405 with three VMs 1410-1420attached, as well as a logical service node 1425. The implementation ofthis logical network, shown on the right side of the figure, includesthe three VMs implemented in three different host machines 1430-1440,and the logical services node (shown with just the DHCP module in thefigure) implemented in two different logical service node hosts 1445 and1450, also referred to as gateways in some embodiments.

Each of the hosts 1430-1440, as well as the gateways 1445 and 1450,includes a managed forwarding element that implements the logical switch1405 (as well as other logical forwarding elements for, e.g., otherlogical networks), although the figure only illustrates the MFE 1455 inthe first host 1430 on which the VM 1410 is implemented.

When the VM 1410 needs an IP address, (e.g., at time of booting up, orwhen renewing a leased address), the VM sends a DHCP discovery messageto the MFE through its virtual interface. In some embodiments, the VMsends this as a broadcast packet. As such, the MFE 1455, implementingthe logical switch 1405, forwards packet to all logical ports of thelogical switch. Therefore, as shown, the packet is sent to each of theVMs 1415 and 1420 (which will ignore the packet, in some embodiments)through tunnels between the MFE 1455 and the MFEs on the hosts 1435 and1440.

In addition, the MFE sends this packet to only the active DHCP service1460 on the gateway 1445 through a tunnel. In some embodiments, the MFEhas information for tunneling packets to both of the gateways, as wellas information indicating that the logical service node operating on thegateway 1445 is the active gateway. The MFE regularly (e.g., every 5seconds, 30 seconds, 2 minutes, etc.) sends out keep-alive messagesthrough the tunnel to the MFE at the gateway. So long as responses arereceived, the MFE 1455 continues sending packets for the logical servicenode 1425 to the gateway 1445. Only if responses to the keep-alivemessages are not received does the MFE send packets for the logicalservice node 1425 to the gateway 1450.

Returning to FIG. 13, the process 1300 uses (at 1310) the source MACaddress of the DHCP discovery packet to generate an offer of an IPaddress and set of options. In some embodiments, based on the MACaddress, the DHCP module identifies the host object, which includes anassigned IP as well as several host-specific options. In addition, thehost object refers to a group/subnet object in some embodiments, whichitself may include several options for all VMs or other hosts on thelogical switch represented by that group. Lastly, the offer includes anyglobal options for all hosts on all logical switches.

The process then sends (at 1315) the generated offer packet with theassigned IP address out through the port of the container from which thediscovery packet was received. In some embodiments, the DHCP modulestores (e.g., in memory) information regarding from which port a DHCPpacket is received, and uses this information when generating a responsepacket. In other embodiments, the namespace stores this information, andis able to direct the response packet to the correct port. In someembodiments, the DHCP module receives packets directly from thenamespace interface by listening on that interface, and therefore knowsto which interface a reply should be sent.

After sending the packet, the process 1300 determines (at 1320) whethera DHCP request packet has been received from the same client (i.e., VMor other host machine) prior to a timeout. In some embodiments, the DHCPmodule sets a time within which a client must request an offered IPaddress (e.g., 1 second, 5 seconds, etc.). When the DHCP module has notreceived the request before timeout, the process ends. On the otherhand, when the DHCP module receives a request packet from the samesource MAC address for the offered IP address, the process sends (at1325) a DHCP acknowledgment packet to the client and stores theassignment of the address (e.g., with a lease time).

This above example assumes a multi-stage DHCP process. Some embodiments,at least for static DHCP, use a shorter process in which the VM sends asingle packet requesting an IP address, and the subsequent response sentby the DHCP module is considered binding. Whereas in traditionalnetworks there might be multiple uncoordinated DHCP servers, in theimplementation of some embodiments shown in, e.g., FIG. 2, only oneactive service is running, and therefore no need exists for the VM tochoose the first of several offers.

In the above examples, each logical service node is implemented by twonamespaces operating in host machines, with one active and one standby.In other embodiments the logical service nodes are configured in anactive/active configuration, in which two (or more) implementations ofthe logical service node (and DHCP service) are active. In thisconfiguration, the MFE 1455 determines to which of the various activeservices to send any DHCP message that it receives from VM 1410 (forother VMs residing on the host 1430, the MFE makes similar decisionsbetween the different DHCP services available for the logical networksof those VMs). When traditional multi-stage DHCP is used (i.e., thediscovery/offer/request/acknowledgement process), the MFE needs toensure that each message sent from a particular VM is sent to the samegateway. Thus, in some embodiments, the MFE 1455 performs a hash of thesource MAC address of a packet (i.e., the MAC address of the requestingVM) and uses the result of this hash to determine to which of thevarious active DHCP services the packet should be sent. Otherembodiments use other determinations, so long as all messages from oneVM go to the same logical service node implementation (i.e., the samegateway).

IV. Electronic System

Many of the above-described features and applications are implemented assoftware processes that are specified as a set of instructions recordedon a computer readable storage medium (also referred to as computerreadable medium). When these instructions are executed by one or moreprocessing unit(s) (e.g., one or more processors, cores of processors,or other processing units), they cause the processing unit(s) to performthe actions indicated in the instructions. Examples of computer readablemedia include, but are not limited to, CD-ROMs, flash drives, RAM chips,hard drives, EPROMs, etc. The computer readable media does not includecarrier waves and electronic signals passing wirelessly or over wiredconnections.

In this specification, the term “software” is meant to include firmwareresiding in read-only memory or applications stored in magnetic storage,which can be read into memory for processing by a processor. Also, insome embodiments, multiple software inventions can be implemented assub-parts of a larger program while remaining distinct softwareinventions. In some embodiments, multiple software inventions can alsobe implemented as separate programs. Finally, any combination ofseparate programs that together implement a software invention describedhere is within the scope of the invention. In some embodiments, thesoftware programs, when installed to operate on one or more electronicsystems, define one or more specific machine implementations thatexecute and perform the operations of the software programs.

FIG. 15 conceptually illustrates an electronic system 1500 with whichsome embodiments of the invention are implemented. The electronic system1500 can be used to execute any of the control, virtualization, oroperating system applications described above. The electronic system1500 may be a computer (e.g., a desktop computer, personal computer,tablet computer, server computer, mainframe, a blade computer etc.),phone, PDA, or any other sort of electronic device. Such an electronicsystem includes various types of computer readable media and interfacesfor various other types of computer readable media. Electronic system1500 includes a bus 1505, processing unit(s) 1510, a system memory 1525,a read-only memory 1530, a permanent storage device 1535, input devices1540, and output devices 1545.

The bus 1505 collectively represents all system, peripheral, and chipsetbuses that communicatively connect the numerous internal devices of theelectronic system 1500. For instance, the bus 1505 communicativelyconnects the processing unit(s) 1510 with the read-only memory 1530, thesystem memory 1525, and the permanent storage device 1535.

From these various memory units, the processing unit(s) 1510 retrieveinstructions to execute and data to process in order to execute theprocesses of the invention. The processing unit(s) may be a singleprocessor or a multi-core processor in different embodiments.

The read-only-memory (ROM) 1530 stores static data and instructions thatare needed by the processing unit(s) 1510 and other modules of theelectronic system. The permanent storage device 1535, on the other hand,is a read-and-write memory device. This device is a non-volatile memoryunit that stores instructions and data even when the electronic system1500 is off. Some embodiments of the invention use a mass-storage device(such as a magnetic or optical disk and its corresponding disk drive) asthe permanent storage device 1535.

Other embodiments use a removable storage device (such as a floppy disk,flash drive, etc.) as the permanent storage device. Like the permanentstorage device 1535, the system memory 1525 is a read-and-write memorydevice. However, unlike storage device 1535, the system memory is avolatile read-and-write memory, such a random access memory. The systemmemory stores some of the instructions and data that the processor needsat runtime. In some embodiments, the invention's processes are stored inthe system memory 1525, the permanent storage device 1535, and/or theread-only memory 1530. From these various memory units, the processingunit(s) 1510 retrieve instructions to execute and data to process inorder to execute the processes of some embodiments.

The bus 1505 also connects to the input and output devices 1540 and1545. The input devices enable the user to communicate information andselect commands to the electronic system. The input devices 1540 includealphanumeric keyboards and pointing devices (also called “cursor controldevices”). The output devices 1545 display images generated by theelectronic system. The output devices include printers and displaydevices, such as cathode ray tubes (CRT) or liquid crystal displays(LCD). Some embodiments include devices such as a touchscreen thatfunction as both input and output devices.

Finally, as shown in FIG. 15, bus 1505 also couples electronic system1500 to a network 1565 through a network adapter (not shown). In thismanner, the computer can be a part of a network of computers (such as alocal area network (“LAN”), a wide area network (“WAN”), or an Intranet,or a network of networks, such as the Internet. Any or all components ofelectronic system 1500 may be used in conjunction with the invention.

Some embodiments include electronic components, such as microprocessors,storage and memory that store computer program instructions in amachine-readable or computer-readable medium (alternatively referred toas computer-readable storage media, machine-readable media, ormachine-readable storage media). Some examples of such computer-readablemedia include RAM, ROM, read-only compact discs (CD-ROM), recordablecompact discs (CD-R), rewritable compact discs (CD-RW), read-onlydigital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a varietyof recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.),flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.),magnetic and/or solid state hard drives, read-only and recordableBlu-Ray® discs, ultra density optical discs, any other optical ormagnetic media, and floppy disks. The computer-readable media may storea computer program that is executable by at least one processing unitand includes sets of instructions for performing various operations.Examples of computer programs or computer code include machine code,such as is produced by a compiler, and files including higher-level codethat are executed by a computer, an electronic component, or amicroprocessor using an interpreter.

While the above discussion primarily refers to microprocessor ormulti-core processors that execute software, some embodiments areperformed by one or more integrated circuits, such as applicationspecific integrated circuits (ASICs) or field programmable gate arrays(FPGAs). In some embodiments, such integrated circuits executeinstructions that are stored on the circuit itself.

As used in this specification, the terms “computer”, “server”,“processor”, and “memory” all refer to electronic or other technologicaldevices. These terms exclude people or groups of people. For thepurposes of the specification, the terms display or displaying meansdisplaying on an electronic device. As used in this specification, theterms “computer readable medium,” “computer readable media,” and“machine readable medium” are entirely restricted to tangible, physicalobjects that store information in a form that is readable by a computer.These terms exclude any wireless signals, wired download signals, andany other ephemeral signals.

While the invention has been described with reference to numerousspecific details, one of ordinary skill in the art will recognize thatthe invention can be embodied in other specific forms without departingfrom the spirit of the invention. In addition, a number of the figures(including FIGS. 5, 7, 9, 10, 12, and 13) conceptually illustrateprocesses. The specific operations of these processes may not beperformed in the exact order shown and described. The specificoperations may not be performed in one continuous series of operations,and different specific operations may be performed in differentembodiments. Furthermore, the process could be implemented using severalsub-processes, or as part of a larger macro process. Thus, one ofordinary skill in the art would understand that the invention is not tobe limited by the foregoing illustrative details, but rather is to bedefined by the appended claims.

We claim:
 1. For a network controller machine comprising anon-transitory machine readable medium and a set of processing units, amethod for managing a plurality of logical networks, the methodcomprising: receiving a specification of a particular logical network ofthe plurality of logical networks, the specification comprisingdefinitions of at least a logical forwarding element and a logicalservice node that provides a logical service to the logical forwardingelement; selecting, from a plurality of host computers designated forhosting logical service nodes for the plurality of logical networks, ahost computer to implement the logical service node of the particularlogical network, said selection based on a set of load balancingcriteria that is defined to distribute operations of the logical servicenode for the plurality of logical networks across the plurality of hostcomputers; based on the definition of the logical service node,generating configuration data to implement the logical service node onthe selected host computer; and distributing the configuration data tothe selected host computer in order for the selected host computer toimplement the logical service node.
 2. The method of claim 1, whereinthe logical forwarding element comprises a logical switch to which aplurality of virtual machines that use the logical service are attached.3. The method of claim 1, wherein the logical forwarding element is afirst logical forwarding element that is attached to a first logicalport of the logical service node, wherein the logical network comprisesa second logical forwarding element that attaches to a second logicalport of the logical service node.
 4. The method of claim 1, wherein theselected host computer comprises a first host computer that hosts anactive implementation of the logical service node, wherein the methodfurther comprises selecting a second host computer to host a standbyimplementation of the logical service node.
 5. The method of claim 1,wherein the logical service comprises a Dynamic Host ConfigurationProtocol (DHCP) service.
 6. The method of claim 5, wherein the logicalservice node provides at least one additional service in addition to theDHCP service.
 7. The method of claim 5, wherein generating theconfiguration data comprises generating a plurality of records defining(i) a container for implementing the logical service node, (ii) DHCPinformation for the logical forwarding element, and (iii) DHCPinformation for a set of virtual machines that attach to the logicalforwarding element.
 8. The method of claim 5, wherein the selected hostcomputer executes a managed forwarding element for forwarding DHCPmessages to the logical service node implemented on the selected hostcomputer.
 9. The method of claim 8, wherein the selected host computerimplements at least two logical service nodes that provide DHCP servicesfor two different logical networks as separate namespaces operating onthe selected host computer, wherein the managed forwarding elementforwards a DHCP message to only one of the separate namespaces based ona logical context appended to the DHCP message.
 10. The method of claim1, wherein the selected host computer implements the logical servicenode as a namespace that operates on the selected host computer.
 11. Themethod of claim 10, wherein the selected host computer implementsadditional logical service nodes for additional logical networks asdifferent namespaces operating on the selected host computer.
 12. Anon-transitory machine readable medium storing a network controllerapplication which when executed by a set of processing units manages aplurality of logical networks, the network controller applicationcomprising sets of instructions for: receiving a specification of aparticular logical network of the plurality of logical networks, thespecification comprising definitions of at least a logical forwardingelement and a logical service node that provides a logical service tothe logical forwarding element; from a plurality of host computersdesignated for hosting logical service nodes for the plurality oflogical networks, selecting a host computer to implement the logicalservice node of the particular logical network based on a set of loadbalancing criteria that is defined to distribute operations of thelogical service node for the plurality of logical networks across theplurality of host computers; based on the definition of the logicalservice node, generating configuration data to implement the logicalservice node on the selected host computer; and distributing theconfiguration data to the selected host computer in order for theselected host computer to implement the logical service node.
 13. Thenon-transitory machine readable medium of claim 12, wherein the logicalforwarding element comprises a logical switch to which a plurality ofvirtual machines that use the logical service are attached.
 14. Thenon-transitory machine readable medium of claim 12, wherein the logicalforwarding element is a first logical forwarding element that isattached to a first logical port of the logical service node, whereinthe logical network comprises a second logical forwarding element thatattaches to a second logical port of the logical service node.
 15. Thenon-transitory machine readable medium of claim 12, wherein the selectedhost computer comprises a first host computer that hosts an activeimplementation of the logical service node, wherein the networkcontroller application further comprises a set of instructions forselecting a second host computer to host a standby implementation of thelogical service node.
 16. The non-transitory machine readable medium ofclaim 12, wherein the logical service comprises a Dynamic HostConfiguration Protocol (DHCP) service.
 17. The non-transitory machinereadable medium of claim 16, wherein the logical service node providesat least one additional service in addition to the DHCP service.
 18. Thenon-transitory machine readable medium of claim 16, wherein the set ofinstructions for generating the configuration data comprises a set ofinstructions for generating a plurality of records defining (i) acontainer for implementing the logical service node, (ii) DHCPinformation for the logical forwarding element, and (iii) DHCPinformation for a set of virtual machines that attach to the logicalforwarding element.
 19. The non-transitory machine readable medium ofclaim 16, wherein the selected host computer executes a managedforwarding element for forwarding DHCP messages to the logical servicenode implemented on the selected host computer.
 20. The non-transitorymachine readable medium of claim 19, wherein the selected host computerimplements at least two logical service nodes that provide DHCP servicesfor two different logical networks as separate namespaces operating onthe selected host computer, wherein the managed forwarding elementforwards a DHCP message to only one of the separate namespaces based ona logical context appended to the DHCP message.
 21. The non-transitorymachine readable medium of claim 12, wherein the selected host computerimplements the logical service node as a namespace that operates on theselected host computer.
 22. The non-transitory machine readable mediumof claim 21, wherein the selected host computer implements additionallogical service nodes for additional logical networks as differentnamespaces operating on the selected host computer.